Sourced from Azure.Messaging.ServiceBus's releases.

7.20.2

7.20.2 (2026-07-08)

Acknowledgments

Thank you to our developer community members who helped to make the Service Bus client library better with their contributions to this release:

• Daniel Marbach (GitHub)

Bugs Fixed

• Fixed a bug where ServiceBusAdministrationClient operations (such as GetQueueAsync, GetTopicAsync, QueueExistsAsync, and TopicExistsAsync) threw a ServiceBusException wrapping an ArgumentException ("Value cannot be empty or contain only white-space characters") when an entity had a shared access authorization rule whose key values were masked (returned empty) by the service for callers lacking the listkeys/action permission. The deserialization path now accepts empty key values, and creating CreateQueueOptions/CreateTopicOptions from the returned properties no longer throws, matching the behavior of the other Azure Service Bus SDKs. (#​60469)

• Fixed a bug in the ServiceBusProcessor where terminal errors (such as DNS resolution failures) caused a tight retry loop with no delay between attempts, potentially overwhelming logs and consuming excessive resources. (#​54572)

• Fixed a race condition in AmqpSender where concurrent calls to CreateMessageBatchAsync during initial AMQP link creation could observe an inconsistent MaxBatchSize, causing a spurious ArgumentOutOfRangeException. (#​56301)

• The sender now reads the com.microsoft:max-message-batch-size vendor property from the AMQP link to correctly limit batch size on Premium large-message entities, where max-message-size can be up to 100 MB but the batch limit is 1 MB. The 4,500 message count cap on batches has been removed as the service does not enforce a count limit. (#​44914)

Other Changes

• Several areas of the AMQP transport integration have been cleaned up, modernized, and made more efficient. (A community contribution, courtesy of danielmarbach)

Commits viewable in compare view.